Great effort! Overall, a bit frustrating that we need to introduce a separate tagging convention just for a single service type (nodejs). Are there any alternatives that do not affect the tagging? @jrwbabylonlab

This also breaks the automated devnet deployment for the simple-staking service on babylon-service-deployment:

https://github.com/babylonlabs-io/babylon-service-deployment/blob/330243364dd7f984e337bd00069b50c87423c5e2/.github/workflows/commit-schedule-checker.yml#L82

Not i'm aware of. FE deployment is always quite different to others as it does not dynamically accept envs.
All code/env need to be ready at build time as webpack will bundle them together

@maiquanghiep it's best to squash merge. otherwise we end up with too many random commits

@jrwbabylonlab Sorry my bad, selected squash but forgot to do the same after reloading the page